home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
comm
/
jmd4tlx.zip
/
JXFER.DOC
< prev
next >
Wrap
Text File
|
1989-03-20
|
15KB
|
382 lines
ENHANCED JMODEM FILE TRANSFERS
using
THE TELIX SALT LANGUAGE
by
Michael K. Bozovich
03/20/89
-----PHILOSOPHY------------------------------------------------------
When I first began using the Jmodem protocol, I was blown away!
I had been using Zmodem and thought that there was no way to beat
it's file transfer rate. At the same time, I was dismayed by the
limitation of one file per transfer. After considering this dilemma,
I set out to to enhance the capabilities of the basic Jmodem driver
in the hopes that the use of this advanced protocol would become
widespread. This set of scripts is at least a step in the right
direction. . .
This set of TELIX 3.11 script files will allow the seamless (almost)
integration of the JMODEM protocol into the TELIX program.
-----PROGRAMS--------------------------------------------------------
The files in this package should consist of:
JXFER.DOC // These instructions.
JUP.SLT // Source code for the upload stub.
JUP.SLC // Compiled upload stub.
JDOWN.SLT // Source code for the download stub.
JDOWN.SLC // Compiled download stub.
JXFER.SLT // Source code for the "inner workings".
JXFER.SLC // Compiled "inner workings".
JSIZE.C // Source code for the "kludge".
JSIZE.EXE // Compiled "kludge".
JMODEM.COM // The Jmodem driver.
JMODEM.DOC // The Jmodem Documentation.
-----INSTALLATION----------------------------------------------------
A. The first step in integrating Jmodem is to tell TELIX the following
in the "File transfer protocols" Setup screen:
1. Key - Whatever you like. (I use "J".)
2. Protocol Name - "Jmodem"
3. Upload Filename - "JUP"
4. Download Filename - "JDOWN"
5. BAT or Script - "Script"
6. DL Name - "N"
Your screen should resemble this:
╒═╡ File transfer protocols ╞══════════════════════════════════════════╕
│ │
│ External Key Protocol Upload Download BAT or DL │
│ Protocols Name Filename Filename Script Name │
│ │
│ A................. J Jmodem JUP JDOWN Script N │
│ │
│ B................. │
│ │
B. The next step is making sure that all of the necessary files are where
they belong:
1. The following files belong in the "Script directory".
This is where you told TELIX to look for script files.
(Option "C" in the filename/path setup.)
JUP.SLC
JDOWN.SLC
JXFER.SLC
2. These files must reside somewhere in the DOS PATH.
If they are not there, don't say I didn't tell you!
JMODEM.COM
JSIZE.EXE
C. That's all there is to it. You can begin using JMODEM with
TELIX as though it came with the package!
-----USAGE-----------------------------------------------------------
These script files provide much more versatility than the standard
"BATCH file" method of adding an external protocol. These are some
points to consider:
1. UPLOAD -
Although some BBS's don't support it (yet), for those that
do, you can now use JMODEM to Batch Upload as many filespecs
as you can fit in the "upload box". You are free to use
wildcards as well. All I ask (and the script file requires!),
is that you include ONE OR MORE SPACES between multiple
filespecs.
2. DOWNLOAD -
Although TELIX doesn't allow multiple filespecs to be
entered in the "download box", the JDOWN script file
will accept them without a hitch. This was accomplished
by supplying an emulation of the "download box". This
WILL NOT WORK if you didn't tell TELIX to not prompt
for the download file name as instructed above!
You MAY NOT use wildcards in your download filespecs.
If you attempt to do so, the script will gripe about
it and grind to a halt. Sorry. I will include this
feature as soon as JMODEM recognizes the name of the
incoming file.
3. PERFORMANCE LOGGING -
In addition to the features described above, this set
of scripts will create and maintain a log file of all
attempted JMODEM transfers. If you have defined a
TELIX environment variable as described in the TELIX
documentation, the file will be placed there. If not,
the file will be written indiscriminately to whatever
drive and subdirectory you happen to be in at the time.
This file is named JMODEM.LOG (catchy, eh?), and is
based on the log file produced by the DSZ.COM program.
Here is a sample:
TELIX JMODEM File Transfer Log
S 7504 2400 bps 0 cps 17s 03-19-89 *ABORTED* \config.sys
R 8388 2400 bps 247 cps 34s 03-19-89 COMPLETED c:\dl\any.zip
S 15112 2400 bps 0 cps 17s 03-19-89 *ABORTED* a:\autoexec.bat
R 26796 2400 bps 245 cps 109s 03-19-89 COMPLETED f:\dl\foo.zip
R 18208 2400 bps 247 cps 74s 03-19-89 COMPLETED .\bar.zip
- The first field indicates whether a (S)end or a (R)eceive
was attempted.
- The second field is the number of bytes transferred.
- The third field is the baud rate used for the transfer.
- The fourth field is a measure of the approximate trans-
fer speed in characters per second. Actual transfer
rates will be greater than those reported. This rate
is set to zero if the transfer was aborted.
- The fifth field is an approximation of the transfer
time in seconds. Since this time includes the time
required to load the JMODEM driver from disk, it's
accuracy depends largly on the speed of the drive
used. Actual transfer times will be less than those
reported.
- Field six is the date the transfer was attempted.
- Field seven indicates whether the transfer met
with success.
- Finally, field eight is the complete specification
of the file involved.
4. PATH SUPPORT -
The pathnames used in uploading/downloading work ex-
actly as described in the TELIX documentation. Here
is a review:
- If you specify a path in the filespec, the script
will respect your wishes.
- If you do not specify a path, the script will use
the one you specified in 'setup'.
- If you did not specify a path in 'setup' (shame!),
the file will end up